Skip to content

Conversation

@taranvohra
Copy link
Contributor

@markerikson I refactored twitter-lite in the same way stockticker was refactored i.e. store having multiple slices. Please have a look. However, there are some things that have been untouched such as the <TwitterLite /> component where there were some connect calls which maybe you would be able to explain better (their purpose)

@markerikson
Copy link
Collaborator

@taranvohra : I actually haven't looked at this particular example myself. I know @cellog put it together based on a performance issue that Twitter filed, in reduxjs/react-redux#686 .

@markerikson markerikson merged commit 2ba0aea into reduxjs:master Sep 23, 2018
@cellog
Copy link
Collaborator

cellog commented Sep 23, 2018

The Twitter-lite benchmark tests a constantly growing array, and is essentially unrealistic and unrelated to the issue it came from. Their issue seemed to be time between mapstate and render increased, but I haven't heard back yet to see if that is indeed true. If so, then we would need to use a different approach to run it. So basically, this benchmark can be made into anything we would like it to be

Aslemammad pushed a commit to Aslemammad/react-state-benchmarks that referenced this pull request May 30, 2021
* setup

* stockticker refactored

* randomized slice and pair to update"

* twitterlite refactored
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants